wip: postfilter rematch#27
Open
vsoch wants to merge 2 commits into
Open
Conversation
vsoch
force-pushed
the
add-reserve-cleanup
branch
from
7fe3280 to
085f76d
Compare
I want to support having other filters (extension points) running with fluence, which means that fluence might make a scheduling decision that is then rejected by some other plugin. If this happens we need to cancel the allocation and record the node names to give as constraints the next time around. This will likely take me a few days to work on, and I am thinking we want to replicate our original experiments in this paper to demosntrate the basic gang scheduling before we go into quantum / custom resources. Signed-off-by: vsoch <vsoch@users.noreply.github.com>
vsoch
force-pushed
the
add-reserve-cleanup
branch
from
085f76d to
b3b6716
Compare
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
vsoch
force-pushed
the
add-reserve-cleanup
branch
from
35948e2 to
dd72a7c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I want to support having other filters (extension points) running with fluence, which means that fluence might make a scheduling decision that is then rejected by some other plugin. If this happens we need to cancel the allocation and record the node names to give as constraints the next time around. This will likely take me a few days to work on, and I am thinking we want to replicate our original experiments in this paper to demosntrate the basic gang scheduling before we go into quantum / custom resources.
I'm really pooped and driving into the city tomorrow so not going to do more work tonight.